Repository navigation
test: изолированные dev-данные для завершения приемки PR517 - #855
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Completes the remaining PR #517 dev acceptance setup without changing existing programs, works or grades. Adds a dev-only, preview-by-default operation that creates four private QA programs: legacy Project, case Solution, open-evaluation hackathon, and noncompetitive Solution.
The explicit apply creates four Project drafts and 23 Solutions (four submitted), using the existing test accounts and 18 new accounts with unusable passwords and reserved
.invalidaddresses. No emails, certificates, grades or assignments are created. All creation flags are closed inside the same transaction. Hash checks enforce preservation of every preexisting row in partner_programs, projects and project_rates, including through tables; a mismatch rolls back the entire setup. A fresh key and a server-side receipt prevent accidental replay.Validation: three real Django/PostgreSQL tests pass, including read-only preview, private bounded apply with no mail, and complete rollback when an old row is deliberately changed. Flake8, Black formatting API and diff checks pass. The workflow retains dev-ref, source SHA and image checks; production deployment is unchanged.